Adding tests for RTCDataChannel id attribute. (#5742) When no ID argument is provided, and the DTLS role hasn't been determined, the id attribute should return `null`. After the DTLS role is determined by an answer being applied with "a=setup:active" (or "passive"), the null IDs should be replaced with either odd or even IDs, depending on the negotiated role. Allow any distinct odd/even IDs; don't require "0, 2, 4, ..."
diff --git a/webrtc/RTCPeerConnection-createDataChannel.html b/webrtc/RTCPeerConnection-createDataChannel.html index cb05e2c..9a50b18 100644 --- a/webrtc/RTCPeerConnection-createDataChannel.html +++ b/webrtc/RTCPeerConnection-createDataChannel.html
@@ -29,8 +29,9 @@ assert_equals(channel.maxRetransmits, null, 'maxRetransmits'); assert_equals(channel.protocol, '', 'protocol'); assert_equals(channel.negotiated, false, 'negotiated'); - // Initial id value is not defined. - assert_equals(typeof channel.id, 'number', 'id type'); + // Since no offer/answer exchange has occurred yet, the DTLS role is unknown + // and so the ID should be null. + assert_equals(channel.id, null, 'id'); assert_equals(channel.priority, 'low', 'priority'); }, 'createDataChannel defaults');
